Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docs and code for remaining references to 'custom bundle' #2732

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

andyw8
Copy link
Contributor

@andyw8 andyw8 commented Oct 17, 2024

Following up from #2615 (comment)

@andyw8 andyw8 added the chore Chore task label Oct 17, 2024
@andyw8 andyw8 requested a review from a team as a code owner October 17, 2024 12:55
@andyw8 andyw8 force-pushed the andyw8/rename-custom-bundle branch 2 times, most recently from 9f9935b to a1a152a Compare October 17, 2024 13:00
@andyw8 andyw8 changed the title Update docs for remaining references to 'custom bundle' Update docs and code for remaining references to 'custom bundle' Oct 17, 2024
jekyll/design-and-roadmap.markdown Outdated Show resolved Hide resolved
jekyll/troubleshooting.markdown Outdated Show resolved Hide resolved
jekyll/troubleshooting.markdown Outdated Show resolved Hide resolved
vscode/src/client.ts Outdated Show resolved Hide resolved
vscode/src/workspace.ts Outdated Show resolved Hide resolved
@andyw8 andyw8 force-pushed the andyw8/rename-custom-bundle branch from a1a152a to a0c23f8 Compare October 17, 2024 16:12
@@ -202,7 +202,7 @@ def run_bundle_install(bundle_gemfile = @gemfile)
end

# If `ruby-lsp` and `debug` (and potentially `ruby-lsp-rails`) are already in the Gemfile, then we shouldn't try
# to upgrade them or else we'll produce undesired source control changes. If the custom bundle was just created
# to upgrade them or else we'll produce undesired source control changes. If the composed bundle was just created
# and any of `ruby-lsp`, `ruby-lsp-rails` or `debug` weren't a part of the Gemfile, then we need to run `bundle
# install` for the first time to generate the Gemfile.lock with them included or else Bundler will complain that
# they're missing. We can only update if the custom `.ruby-lsp/Gemfile.lock` already exists and includes all gems
Copy link
Contributor

@alexcrocha alexcrocha Oct 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have references to a composed lockfile. I am assuming this is it. Should we also refer to it here as composed?

Suggested change
# they're missing. We can only update if the custom `.ruby-lsp/Gemfile.lock` already exists and includes all gems
# they're missing. We can only update if the composed `.ruby-lsp/Gemfile.lock` already exists and includes all gems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Chore task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants